Columbia Kermit/kermit.zip/newsgroups/misc.19950726-19950929/[e-mail]_Wed Jul 26 14:28:48 1995.msg

Internet Message Format | 2020-01-01 | 4KB

Received: from apakabar.cc.columbia.edu by watsun.cc.columbia.edu with SMTP id AA14980
  (5.65c+CU/IDA-1.4.4/HLK for <[e-mail]>); Wed, 26 Jul 1995 10:29:00 -0400
Received: by apakabar.cc.columbia.edu id AA02201
  (5.65c+CU/IDA-1.4.4/HLK for kermit.misc@watsun); Wed, 26 Jul 1995 10:28:58 -0400
Path: news.columbia.edu!watsun.cc.columbia.edu!fdc
From: [e-mail] (Frank da Cruz)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: Kermit uploads from DOS to Unix
Date: 26 Jul 1995 14:28:48 GMT
Organization: Columbia University
Lines: 67
Message-Id: <3v5jf0$[e-mail]>
References: <3v3c9v$[e-mail]>
Nntp-Posting-Host: watsun.cc.columbia.edu
Apparently-To: [e-mail]

In article <3v3c9v$[e-mail]>,
Clarence Dold  <[e-mail]> wrote:
>In article <3v16jk$[e-mail]> you wrote:
>
>: I just got the latest version of Kermit from the ftp site and I can't get
>: long-packet transfers to work.  Needless to say, this is very
>: aggravating for me.  I've read the .bwr file, but I can't get any of the
>: suggestions there to work.  Please help!
>
>To go from DOS <-> UNIX, you very likely need a customized file,
>mscustom.ini, copied to your UNIX directory as .kermrc
>
>With some care, the same file can be used on both systems.
>The UNIX version also has to be 188 or higher.
>Lacking a .kermrc on the UNIX side, you will be stuck with non-optimal, but
>reliable, settings.
>
Thanks, Clarence.  But I don't want people to be left with the mistaken
impression that the only way to configure Kermit is with a mysterious
external file (like WIN.INI, etc, for Windows).

Kermit initialization files contain ordinary Kermit commands that can be
typed by anybody at any time.  The ones that we distribute contain
reasonable values, i.e. values that should work for everybody "out of the
box".

Here are a couple rules of thumb we have developed over the years:

 1. You should not change your MSKERMIT.INI or CKERMIT.INI or .kermrc
    file from the standard, distributed one unless you REALLY know what
    you are doing.  Otherwise it's impossible to answer your questions,
    address your problems, etc.

 2. Make all your desired customizations in the MSCUSTOM.INI or CKERMOD.INI
    or .mykermrc file.

Customizations relating to protocol parameters (packet lengths, window
sizes, and particularly control-character unprefixing) should not be made
without some understanding of what you are doing.  If these speedups were
safe for everybody, believe me, we'd make them standard defaults and avoid
the "Kermit is too slow" discussions.  Nothing would be easier than for us
to make:

  SET WINDOW 30
  SET RECEIVE PACKET-LENGTH 5000
  SET CONTROL UNPREFIX ALL

the defaults for everybody.  Unfortunately, many of our computers and
connections are not up to handling protocol defaults beyond the ones that
we already have, and transfers would fail for lots of people.

But don't worry, you don't have to stay up all night cramming in order to
make Kermit go fast.  Try this instead: at the MS-DOS Kermit 3.14 or
C-Kermit 5A(190) prompt, simply type:

  FAST

Do this on both ends, assuming you have one of these programs on each end
(these are the current versions).

Now try to transfer a file.  If it works, and it works without lots of
errors (retransmissions), then you're done.  Otherwise, you'll have to do
a little studying -- but in that case, would also have had to do a little
studying with any other protocol too, because it probably would not have
worked on this connection either.

- Frank